Conversation
- Rename extension slug to in-the-time-zone - Prepare extension for Raycast Store - updates timezones - init - Initial commit
|
Congratulations on your new Raycast extension! 🚀 We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 10-15 business days. Once the PR is approved and merged, the extension will be available on our Store. |
Greptile SummaryThis PR introduces the In The (Time) Zone extension — a timeline visualizer that lets users scrub across time zones with color-coded working/sleeping hours, sunrise/sunset display, and city search. The implementation is well-structured with clean separation between rendering ( Remaining issues found:
Confidence Score: 3/5
Important Files Changed
Last reviewed commit: "feat: update time zo..." |
|
This pull request has been automatically marked as stale because it did not have any recent activity. It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊 |
0xdhrv
left a comment
There was a problem hiding this comment.
Thanks for your contribution 🔥
We already have an extension in the Store that deals with Team Timezone. Could we consider enhancing the existing extension below instead of creating another one?
You can extend the existing extension by adding new commands to it, since it seems to have related functionality.
If there are unique features or workflows you’re aiming to add, we’d love to hear them and see if they can be integrated into this to avoid duplication and improve discoverability.
This would help avoid duplication and keep related functionality consolidated in one place.
As mentioned in our extension guidelines here ↗
Hi @0xdhrv thanks for your comment. If you look at the apps they're fundamentally different. Timezone buddy tries to have the concept of keeping track of your friends in different time zones. My app is designed to figure out what time it is in other time zones, then scrub effectively left and right to figure out the overlaps of reasonable times between different different time zones (thus the name, "in-the-timezone"). Use case:
Fundamentally, it requires taking existing time, and scrubbing back and forth to find the corresponding time across the zones. This does not exist in the others and is philosophically different in it's operations and use. I understand that you forsee an overlap, but I think they're fundamentally different use cases and adding to it would change the philosophy of these two apps. Let me know if you'd like me to define mine more clearly. |
|
This pull request has been automatically marked as stale because it did not have any recent activity. It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊 |
|
@0xdhrv or any other admin , please let me know what the plan is and if I can provide further clarification. Again as I mentioned above I think these are different use cases. |
…atting - Refactor time handling to use getCurrentTimeISO for consistency - Update package.json with new title formatting and dependencies - Enhance timeline rendering with improved markdown generation - Introduce time-utils for GMT offset and delta formatting - Clean up unused functions and streamline code structure - Add ESLint configuration for better code quality
|
@greptileai, could you please do a fresh review of this PR? |
There was a problem hiding this comment.
nitpick: maybe a different icon
If you can choose a slightly more unique icon, that would be great for end users to differentiate it from the other extensions
There was a problem hiding this comment.
issue: metadata image style
The current screenshot has local extension icon in the bottom bar
Could you make sure that the metadata images use the same background/appearance as the rest to maintain the same visual expression?
Reference:
There was a problem hiding this comment.
issue: metadata image style
The current screenshot has local extension icon in the bottom bar
Could you make sure that the metadata images use the same background/appearance as the rest to maintain the same visual expression?
Reference:
There was a problem hiding this comment.
issue: metadata image style
The current screenshot has local extension icon in the bottom bar
Could you make sure that the metadata images use the same background/appearance as the rest to maintain the same visual expression?
Reference:
| { | ||
| "$schema": "https://www.raycast.com/schemas/extension.json", | ||
| "name": "in-the-time-zone", | ||
| "title": "In the (Time) Zone", |
There was a problem hiding this comment.
| "title": "In the (Time) Zone", | |
| "title": "In the Timezone", |
There was a problem hiding this comment.
suggestion: just a suggestion for the title
In case you accept it, please update it for the command's title as well
0xdhrv
left a comment
There was a problem hiding this comment.
Hey @imranidz 👋
Thanks for the contribution and patience.
I have added a few comments related to metadata images for you to address and few suggestions to make it better.
Also, I have updated the extension with some improvements, please take a look at it.
…n structure in getSunTimes
Description
In The (Time) Zone helps you coordinate across time zones effortlessly. See at a glance when your team is available with a color-coded timeline view.
Features:
Timeline View — See all your cities at once with working hours highlighted
Time Scrubbing — Use arrow keys to shift time and instantly see how it affects everyone
Smart Colors — Green (9-5 working), Yellow (7-9, 5-12 marginal), Red (12-7 sleeping)
Sunrise/Sunset — Know when the sun rises and sets in each city
Any City — Search and add any city in the world
Perfect for remote teams, scheduling international meetings, or planning calls with friends abroad.
Screencast
Checklist
npm run buildand tested this distribution build in Raycastassetsfolder are used by the extension itselfREADMEare placed outside of themetadatafolder